feat: Docs for client secret rotation #2424
Open
+131
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SamuelDev
requested review from
aeneasr,
piotrmsc,
unatasha8,
vinckr and
zepatrik
as code owners
SamuelDev
force-pushed
the
client-secret-rotation-docs
branch
from
068aa3d to
5e927b3
Compare
7 tasks
Author
|
Javascript integration test failure seems like a CI issue and unrelated to these changes |
Contributor
|
@wassimoo @unatasha8 would you kindly take a look at this pls? |
vinckr
force-pushed
the
client-secret-rotation-docs
branch
from
19afb45 to
29299a0
Compare
vinckr
reviewed
Feb 11, 2026
Member
vinckr
left a comment
vinckr
left a comment
There was a problem hiding this comment.
lgtm :) fixed some layout issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue or Design Document
Docs updates for client secret rotation
Checklist
If this pull request addresses a security vulnerability,
I confirm that I got approval (please contact security@ory.com) from the maintainers to push the changes.
Further comments